Release 10.1A: OpenEdge Application Server:
Administration

Editing OpenEdge service properties

Default values for the properties of an OpenEdge service are stored in a Sonic ESB resource that is loaded from either a WSM file or a WSD file:

WSM file — After developing your 4GL application, you use the Proxy Generator tool to create a Web Services Mapping (WSM) file. The OpenEdge Adapter for Sonic ESB uses this WSM file to create the corresponding SOAP calls, enabling the application to function as a service on the ESB. See OpenEdge Development: Open Client Introduction and Programming and the Proxy Generator online help for more information.
WSD file — If you intend to deploy an existing WSA-based Web service in the Sonic ESB environment, you can export its service definition from the Progress Explorer tool and use the resulting Web Service Definition (WSD) file instead of a WSM file. By doing so, you preserve the defined properties of the service and avoid the need to modify them again.

If you want to change the defaults, you can do so by using the OpenEdge custom resource editor to modify the file, as explained in the "Editing the default service properties" section. The OpenEdge resource editor also provides the option of generating a Web Services Definition Language (WSDL) file for the service (see the "Generating a WSDL file from the OpenEdge Resource Editor" section).

For any specific service instance, you can override some of the defaults stored in the file by editing the desired values in the Sonic ESB Explorer. You can specify these service-specific values when you create the service instance, and you can edit them after the instance has been defined (see the "Creating an OpenEdge service instance" section). In cases where no value is explicitly defined for a service, the default value is in effect.

By overriding the defaults with service-specific values, you can use the same WSM or WSD resource as the basis for multiple services that differ only with respect to a few details. For example, you might want to create two or more services that provide the same functionality but use the facilities of different AppServers.

Note: Editing the service properties in the Sonic ESB Explorer window does not affect any values stored in the WSM or WSD resource. Conversely, editing the resource does not affect any overrides that were entered for the service instance.

Adding the WSM or WSD resource to the Sonic ESB Directory Service

To make the WSM or WSD file available, you must load the file as a resource into the Sonic ESB Directory Service.

Note: You can load the WSM or WSD file before creating a service instance, as explained in the procedure that follows, or you can do so as part of the process of creating the instance (see the "Creating an OpenEdge service instance" section).

To load the WSM or WSD resource:

Start the SonicMQ container that hosts the Directory Service. Typically this is the SonicMQ Domain Manager.
On the Sonic Management Console menu bar, select Tools and then Sonic ESB Explorer.
In the left pane of the Sonic ESB Explorer window, click the Resources node.
Note: If there is no Resources node, since nothing is currently stored in Resources, see the "Creating an OpenEdge service instance" section.
In the right pane, click New.
Click Load from File. The Load Resource From File window, a standard file browser, appears. Navigate to the WSM or WSD file, select it, and click Open. The right pane of the Sonic ESB Explorer window now shows the name and contents of the file, as shown:



You can change the name of the resource, if you wish, to any name of your choice that is not already in use (but keep the .wsm or .wsd extension). Then click Apply to store the WSM or WSD file in the Directory Service.

Editing the default service properties

Use this procedure to set default properties that will be in effect for services based on a given WSM or WSD file. The values that you specify will apply unless they are overridden for specific service instances.

To edit service defaults:

Start the SonicMQ Domain Manager and open the Sonic ESB Explorer.
In the left pane of the Sonic ESB Explorer window, click the Resources node.
In the resource list at the top of the right pane, locate and select the resource that you want to edit.
Click the Edit button at the bottom of the right pane. The Edit OpenEdge Service Definition window appears, as shown:

,

The Deployment Information tab includes these fields:
Web Service Namespace — The namespace uniquely identifies the service and its elements within the Sonic ESB. It must meet the requirements of an XML namespace value. (This default can be overridden by a service-specific value entered in the Sonic ESB Explorer.)
SOAP Action URI — This is an optional value; if specified, it can be any string. If you enter a value, any client accessing the service as a Web service must place that value in the SOAPAction HTTP header when it invokes operations on the service.

Enter or modify these values as appropriate. Then click the Runtime Properties tab.

The Runtime Properties tab shows the values of various properties that affect execution of the service:



If the service was designed to use the session-managed session model, more properties are listed than are shown in the illustration above. For an explanation of each property, see Appendix A "Reference to Progress 4GL Web Service Properties."

The following properties can be overridden by service-specific values entered in the Sonic ESB Explorer:

appServiceProtocol
appServiceHost
appServicePort
appServiceName
noSessionReuse
noHostVerify

After setting the properties as appropriate, click the Deployment Information tab if you want to generate a WSDL file, or click OK to save your changes and return to the Sonic ESB Explorer.